Skip to content

Introduce MCP component - #20866

Merged
lpramuk merged 1 commit into
SatelliteQE:masterfrom
lpramuk:add_mcp_component
Feb 25, 2026
Merged

Introduce MCP component#20866
lpramuk merged 1 commit into
SatelliteQE:masterfrom
lpramuk:add_mcp_component

Conversation

@lpramuk

@lpramuk lpramuk commented Feb 25, 2026

Copy link
Copy Markdown
Contributor

Problem Statement

MCP component doesn't have its tests

Solution

Align existing MCP tests under MCP component

Related Issues

satelliteqe/satellite-jenkins/-/merge_requests/1870

Summary by Sourcery

Enhancements:

  • Update MCP system test case metadata to use the MCP component and requirement instead of the generic API classification.

@lpramuk lpramuk self-assigned this Feb 25, 2026
@lpramuk
lpramuk requested a review from a team as a code owner February 25, 2026 13:00
@lpramuk lpramuk added CherryPick PR needs CherryPick to previous branches AutoMerge_Cherry_Picked The cherrypicked PRs of master PR would be automerged if all checks passing 6.18.z Introduced in or relating directly to Satellite 6.18 6.19.z labels Feb 25, 2026
@sourcery-ai

sourcery-ai Bot commented Feb 25, 2026

Copy link
Copy Markdown
Contributor
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Retags the existing MCP system test to use the MCP component and requirement metadata instead of API, aligning it with the new MCP component classification.

File-Level Changes

Change Details Files
Align MCP system test metadata with the MCP component.
  • Update :CaseComponent: field from API to MCP to categorize the test under the MCP component.
  • Update :Requirement: field from API to MCP to match the new component classification.
tests/foreman/sys/test_mcp.py

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@adamlazik1 adamlazik1 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lpramuk

lpramuk commented Feb 25, 2026

Copy link
Copy Markdown
Contributor Author

trigger: test-robottelo
pytest: -v tests/foreman/sys/test_mcp.py::test_positive_call_mcp_server[downstream]

@Satellite-QE

Copy link
Copy Markdown
Collaborator

PRT Result

Build Number: 14465
Build Status: UNSTABLE
PRT Comment: pytest -v tests/foreman/sys/test_mcp.py::test_positive_call_mcp_server[downstream] --external-logging
Test Result : ================== 1 failed, 6 warnings in 814.18s (0:13:34) ===================

@Satellite-QE Satellite-QE added the PRT-Failed Indicates that latest PRT run is failed for the PR label Feb 25, 2026
@lpramuk
lpramuk merged commit 47f6c05 into SatelliteQE:master Feb 25, 2026
13 of 14 checks passed
github-actions Bot pushed a commit that referenced this pull request Feb 25, 2026
(cherry picked from commit 47f6c05)
github-actions Bot pushed a commit that referenced this pull request Feb 25, 2026
(cherry picked from commit 47f6c05)
lpramuk added a commit that referenced this pull request Feb 25, 2026
Introduce MCP component (#20866)

(cherry picked from commit 47f6c05)

Co-authored-by: Lukas Pramuk <lpramuk@redhat.com>
lpramuk added a commit that referenced this pull request Feb 25, 2026
Introduce MCP component (#20866)

(cherry picked from commit 47f6c05)

Co-authored-by: Lukas Pramuk <lpramuk@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.18.z Introduced in or relating directly to Satellite 6.18 6.19.z AutoMerge_Cherry_Picked The cherrypicked PRs of master PR would be automerged if all checks passing CherryPick PR needs CherryPick to previous branches PRT-Failed Indicates that latest PRT run is failed for the PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants